Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1472

reference: 911-tree-1
name: 1472
tree-preservation-order: undefined
911-tpo-1
uprn
address-text
point: POINT (-1.046371 50.867224)
geometry: MULTIPOLYGON (((-1.046329 50.867220,-1.046331 50.867228,-1.046337 50.867236,-1.046346 50.867242,-1.046358 50.867246,-1.046371 50.867247,-1.046384 50.867246,-1.046396 50.867242,-1.046406 50.867236,-1.046412 50.867229,-1.046414 50.867220,-1.046412 50.867212,-1.046406 50.867204,-1.046397 50.867198,-1.046385 50.867194,-1.046372 50.867193,-1.046359 50.867194,-1.046347 50.867198,-1.046337 50.867204,-1.046331 50.867211,-1.046329 50.867220)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL